Skip to content

Conversation

@ameliahsu
Copy link
Member

add query param to filter by integrationType:

  • messaging
  • project_management
  • source_code_management
  • on_call_scheduling

@ameliahsu ameliahsu requested review from a team as code owners October 4, 2024 22:03
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 4, 2024
)
assert response.data == []

def test_integration_type(self):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: maybe add a test for what happens when u pass both providerKey and integrationType
also maybe throw docs in ur backlog

@iamrajjoshi iamrajjoshi requested a review from a team October 7, 2024 21:52
DEPLOYMENT = "deployment"


# Integration Types
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm i would love to do something so that when you register the integrations here

for integration_path in settings.SENTRY_DEFAULT_INTEGRATIONS:
try:
integration_cls = import_string(integration_path)
except Exception:
import traceback
click.echo(
f"Failed to load integration {integration_path!r}:\n{traceback.format_exc()}",
err=True,
)
else:
integrations.register(integration_cls)
for integration in integrations.all():
try:
integration.setup()
except AttributeError:
pass

you also register the integration type... cc @RyanSkonnord if you have thoughts

IntegrationProviderSlug.DISCORD,
IntegrationProviderSlug.MSTeams,
],
PROJECT_MANAGEMENT: [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many (or all) of source code management integrations are also project management ones. At least Github and Azure are. @cathteng can confirm which ones for sure.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are we grouping integrations by the main focus or by a particular feature? i would say the ticketing aspect of SCMs is a feature

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sentaur-athena @cathteng I just grouped them based on our integration feature list

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cathteng we can come back and update this list since it's not really used anywhere in code other than messaging. My thought is for example if we want to build onboarding and tell people we have these ticket management integrations we still want to return github in that list.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@ameliahsu ameliahsu merged commit 6e3a1e1 into master Oct 8, 2024
49 checks passed
@ameliahsu ameliahsu deleted the mia/proj-creation/api-filter branch October 8, 2024 20:16
@github-actions github-actions bot locked and limited conversation to collaborators Oct 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants